Data loss prevention for an online content management platform

ABSTRACT

Disclosed are systems, methods, and non-transitory computer-readable storage media for providing content management features in a messaging service. A content management system is configured to receive an update to a rule in a data loss prevention (DLP) policy, to identify, based on a log of DLP violations, one or more content items for updating content management permissions, and to update the content management permissions for the one or more content items based on the update to the rule.

CROSS-REFERENCE TO RELATED APPLICATIONS

The application is a divisional of U.S. application Ser. No. 15/392,428filed Dec. 28, 2016, entitled “Data Loss Prevention for an OnlineContent Management Platform”, which is hereby expressly incorporatedherein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to online content managementservices and in particular to providing data loss prevention featureswithin a content management platform.

BACKGROUND

Online content management services allow users to access and managecontent across multiple devices using the Internet. In a typical onlinecontent management service, a user establishes a content managementaccount with the service provider and can associate various contentitems with the content management account. For example, online contentmanagement services may allow the user to store content items (includingbut not limited to text documents; email messages; text messages; othertypes of messages; media files such as photos, videos, and audio files;and/or folders containing multiple files). Some online contentmanagement services may allow users to set sharing options for storedcontent items in order to control whether and how other users are ableto access the content items.

Data loss prevention (DLP) strategies are designed to address the riskof inadvertent leaks or exposure of sensitive data outside of authorizedchannels. Some DLP services work with content management platforms bysitting between the end user and the content management platform. On anupload, a DLP service may first obtain the content item from a userdevice, scan the content item, and, if permitted, upload the contentitem to the content management platform. On a download, the DLP servicemay first obtain the content item from the content management platform,scan the content item, and, if permitted, send the content item to theuser device.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the presenttechnology will become apparent by reference to specific implementationsillustrated in the appended drawings. A person of ordinary skill in theart will understand that these drawings only show some examples of thepresent technology and would not limit the scope of the presenttechnology to these examples. Furthermore, the skilled artisan willappreciate the principles of the present technology as described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIG. 1 shows an example of a content management system and clientdevices according to some embodiments;

FIG. 2 shows an example graphical user interface for enabling data lossprevention (DLP) features in a content management system according tosome embodiments;

FIG. 3 shows an example graphical user interface for configuring dataloss prevention (DLP) features in a content management system accordingto some embodiments;

FIG. 4 shows an example graphical user interface for accessing contentitems stored on a content management system according to someembodiments;

FIG. 5 shows an example graphical user interface for accessing contentitems stored on a content management system according to someembodiments;

FIG. 6 shows an example graphical user interface for displaying a dataloss prevention (DLP) report according to some embodiments;

FIG. 7 shows an example method for providing data loss prevention (DLP)features in a content management system according to some embodiments;

FIG. 8 shows an example method for responding to a removal of a rulefrom a DLP policy according to some embodiments;

FIG. 9 shows an example method for responding to a change to a conditionin a rule in a DLP policy according to some embodiments;

FIG. 10 shows an example method for responding to a change to arestriction in a rule in a DLP policy according to some embodiments;

FIG. 11 shows an example of a system for implementing certain aspects ofthe present technology.

DETAILED DESCRIPTION

Various examples of the present technology are discussed in detailbelow. While specific implementations are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfigurations may be used without parting from the spirit and scope ofthe present technology.

The disclosed technology addresses the need in the art for integratingdata loss prevention (DLP) features within an online content managementsystem. Inadvertent leaks or exposure of sensitive data has long been athreat to individuals and organizations. However, new technical problemshave arisen with the advent and wide adoption of computer and internettechnologies that facilitate the convenient storage and dissemination ofdata, especially within the context of remote content management systemsaccessible via a network. For example, DLP services that sit between anend user and a content management system scan content items as they aredownloaded or uploaded by a user device. However, this requires that thecontent items be transmitted over a network and scanned by the DLPservices each time a content item is uploaded or downloaded, thusincreasing the strain on network bandwidth, processing, and additionaldelay for the end user waiting for the content item to be scanned. Thesecomputing resources are further wasted when, as a result of the scan, itis discovered that the content item is not permitted to be uploaded,downloaded, or shared.

Furthermore, a DLP service that sits between an end user and a contentmanagement system can enforce DLP policies on the content item only andnot metadata associated with the content item but stored separately andonly while the content item is under the service's control. For example,a DLP service no longer has the ability to affect access of a contentitem after the DLP service delivers the content item to the user deviceor the content management system. For example, a DLP service can scan acontent item and allow the content item to be downloaded by a user basedon one set of rules. If an administrator later updates the rules suchthat the content item is no longer allowed to be downloaded by thatuser, the DLP service is unable to stop access to the content item bythat user.

The disclosed technology overcomes many of these technical obstacles andenables further data loss prevention (DLP) features within an onlinecontent management system. Some embodiments use a sharing service withina content management system to establish and enforce a DLP policycontaining a number of rules. The content management system may scancontent items stored on the content management system and generate a logof DLP violations that contains a record of each violation of the DLPpolicy. For example, the record may reference the content items thatviolated a rule in the DLP policy and a reference to rule that wasviolated.

An administrator may update the DLP policy to add new rules, removerules, or change existing rules. If a rule was updated, the contentmanagement system may identify, based on the log of DLP violations, oneor more content items that were flagged as having violated the old ruleand update the permissions for those content items based on the updateto the rule. In some embodiments, the content management system mayrescan content items as appropriate, based on the update to the rule.Because the content management system has persistent access to thecontent items, the scan of the content items may be performed in thebackground or when computing resources are available and not causeadditional delay for end users when accessing content. Furthermore, insome embodiments, every content item does not need to be rescanned foreach change to a rule in the DLP policy. Instead, methods and systemsdescribed with respect to various embodiments provide for moreintelligent processing of content items in response to changes in arule.

As will be discussed in further detail below, in some embodiments, thecontent management system is able to facilitate collaboration betweenusers. Collaboration features include content item sharing, commentingon content items, co-working on content items, instant messaging,providing presence and seen state information regarding content items,etc. Much of the collaborative data or elements (e.g., comments,annotations, or other collaboration content item elements) related tothe content items resides on the content management system and is storedseparately from the content item and, as such, may not be scanned by aDLP service that sits between an end user and a content managementsystem. Some embodiments of subject technology allow for the sharingservice within the content management system to scan the content itemsas well as the collaborative data associated with the content item thatis stored on the content management system.

In some embodiments, the disclosed technology is deployed in the contextof a content management system having content item synchronizationcapabilities and collaboration features, among others. An example systemconfiguration 100 is shown in FIG. 1, which includes content managementsystem 110 interacting with client device 150.

Accounts

Content management system 110 can store content items in associationwith accounts, as well as perform a variety of content item managementtasks, such as retrieve, modify, browse, and/or share the contentitem(s). Furthermore, content management system 110 can enable anaccount to access content item(s) from multiple client devices.

Content management system 110 supports a plurality of accounts. Anentity (user, group of users, company, etc.) can create an account withcontent management system, and account details can be stored in accountdatabase 145. Account database 140 can store profile information forregistered entities. In some cases, profile information for a registeredentity can include a username and/or email address. Account database 140can include account management information, such as account type (e.g.various tiers of free or paid accounts), storage space allocated,storage space used, client devices 150 having a registered contentmanagement client application 152 resident thereon, security settings,personal configuration settings, etc.

Account database 140 can store groups of accounts associated with anentity. Groups can have permissions based on group policies (e.g., dataloss prevention policies) and/or access control lists, and members of agroup can inherit the permissions. For example, a marketing group canhave access to one set of content items while an engineering group canhave access to another set of content items. An administrative group canmodify groups, modify user accounts, etc.

Content Item Storage

A feature of content management system 110 is the storage of contentitems, which can be stored in content storage 142. Content items can beany digital data such as documents, collaboration content items, textfiles, audio files, image files, video files, webpages, executablefiles, binary files, etc. A content item can also include collections orother mechanisms for grouping content items together with differentbehaviors, such as folders, zip files, playlists, albums, etc. Acollection can refer to a folder, or a plurality of content items thatare related or grouped by a common attribute. In some embodiments,content storage 142 can be combined with other types of storage ordatabases to handle specific functions. Content storage 142 can storecontent items, while metadata regarding the content items can be storedin metadata database 146. Likewise, data regarding where a content itemis stored in content storage 142 can be stored in content directory 144.Additionally, data regarding changes, access, etc. can be stored inserver file journal 148. Each of the various storages/databases such ascontent storage 142, content directory 144, server file journal 148, andmetadata database 146 can be comprised of more than one such storage ordatabase and can be distributed over many devices and locations. Otherconfigurations are also possible. For example, data from content storage142, content directory 144, server file journal 148, and/or metadatadatabase 146 may be combined into one or more content storages ordatabases or further segmented into additional content storages ordatabases. Thus, content management system 110 may include more or lessstorages and/or databases than shown in FIG. 1.

In some embodiments, content storage 142 is associated with at least onecontent management service 116, which includes software or otherprocessor executable instructions for managing the storage of contentitems including, but not limited to, receiving content items forstorage, preparing content items for storage, selecting a storagelocation for the content item, retrieving content items from storage,etc. In some embodiments, content management service 116 can divide acontent item into smaller blocks of data for storage at content storage142. The location of each data block making up a content item can berecorded in content directory 144. Content directory 144 can include acontent entry for each content item stored in content storage 142. Thecontent entry can be associated with a unique ID, which identifies acontent item.

In some embodiments, the unique ID, which identifies a content item incontent directory 144, can be derived from a deterministic hashfunction. This method of deriving a unique ID for a content item canalmost always ensure that content item duplicates are recognized as suchsince the deterministic hash function will generally output the sameidentifier for every copy of the same content item, but will output adifferent identifier for a different content item. Using thismethodology, content management service 116 can output a unique ID foreach content item.

Content management service 116 can also designate or record a contentpath for a content item. The content path can include the name of thecontent item and/or folder hierarchy associated with the content item.For example, the content path can include a folder or path of folders inwhich the content item is stored in a local file system on a clientdevice. Content management service 116 can use the content path topresent the content items in the appropriate folder hierarchy, such as atree-like directory structure. While content items are stored in contentstorage 142 in blocks and may not be stored under a tree like directorystructure, such directory structure is a comfortable navigationstructure for users Content management service 116 can define or recorda content path for a content item wherein the “root” node of a directorystructure can be a namespace for each account. Within the namespace canbe a directory structure defined by a user of an account and/or contentmanagement service 116. Content directory 144 can store the content pathfor each content item as part of a content entry.

In some embodiments, the namespace can include additional namespacesthat appear in the directory structure as if they are stored within theroot node. This can occur when an account has access to a sharedcollection. Shared collections can be assigned their own namespacewithin content management system 110. While shared collections areactually a root node for the shared collection, they are locatedsubordinate to the user account namespace in the directory structure,and can appear as a folder within a folder for the user account. Asaddressed above, the directory structure can be a comfortable navigationstructure for users, but does not necessarily correlate to storagelocations of content items in content storage 142.

While the directory structure in which an account views content itemsdoes not necessarily correlate to storage locations at contentmanagement system 110, the directory structure can generally correlateto storage locations on client device 150 depending on the file systemused by client device 150.

As addressed above, a content entry in content directory 144 can alsoinclude the location of each block of data making up a content item.More specifically, the content entry can include content pointers thatidentify the location in content storage 142 of the data blocks thatmake up the content item.

In addition to a content path and content pointer, a content entry incontent directory 144 can also include a user account identifier thatidentifies the user account that has access to the content item and/or agroup identifier that identifies a group with access to the contentitem. In some embodiments, multiple user account identifiers can beassociated with a single content entry indicating that the content itemhas shared access by the multiple user accounts. In some embodiments,user account identifiers associated with a single content entry canspecify different permissions for the associated content item. In someembodiments, content directory 144 can describe a hierarchical structureof content items associated with a user account, the hierarchicalstructure being specific to the user account.

Content management service 116 can decrease the amount of storage spacerequired by identifying duplicate content items or duplicate blocks thatmake up a content item or versions of a content item. Instead of storingmultiple copies, content storage 142 can store a single copy of thecontent item or block of the content item and content directory 144 caninclude a pointer or other mechanism to link the duplicates to thesingle copy.

Content management service 116 can also store metadata describingcontent items, content item types, folders, file path, and/or therelationship of content items to various accounts, collections, orgroups in metadata database 146, in association with the unique ID ofthe content item.

Content management service 116 can also store a log of data regardingchanges, access, etc. in server file journal 148. Server file journal148 can include the unique ID of the content item and a description ofthe change or access action along with a time stamp or version numberand any other relevant data. Server file journal 148 can also includepointers to blocks affected by the change or content item access.Content management service can provide the ability to undo operations,by using a content item version control system that tracks changes tocontent items, different versions of content items (including divergingversion trees), and a change history that can be acquired from theserver file journal 148. The change history can include a set of changesthat, when applied to the original content item version, produces thechanged content item version.

Content Item Synchronization

Another feature of content management system 110 is synchronization ofcontent items with at least one client device 150. Client device(s) cantake different forms and have different capabilities. For example,client device 170 is a computing device having a local file systemaccessible by multiple applications executing on the device. Clientdevice 172 is a computing device in which content items may only beaccessible to a specific application or by permission given by thespecific application, and the content items can be stored in anapplication specific space and/or in a remote network. Client device 174is any client device accessing content management system 110 via a webbrowser and accessing content items via a web interface. While exampleclient devices 170, 172, and 174 are depicted in form factors such as alaptop, mobile device, or web browser, it should be understood thatthese descriptions do not limit clients devices to these form factors.For example, a mobile device, such as client device 172, may have alocal file system accessible by multiple applications executing on thedevice, or client device 172 may access content management system 110via a web browser. As such, the form factor should not be consideredlimiting when considering client device 150's capabilities. One or morefunctions described in this disclosure with respect to client device 150may or may not be available on every client device depending on thespecific capabilities of the device—the file access model being one suchcapability.

In many embodiments, client devices are associated with an account ofcontent management system 110, but in some embodiments, client devicescan access content using shared links and do not require an account.

As noted above, some client devices can access content management system110 using a web browser. However, client devices can also access contentmanagement system 110 using client application 152 stored and running onclient device 150. Client application 152 can include a content itemsynchronization service 156.

Content item synchronization service 156 can be in communication withcontent management service 116 to synchronize changes to content itemsbetween client device 150 and content management system 110.

Client device 150 can synchronize content with content management system110 via content synchronization service 156. The synchronization can beplatform agnostic. That is, content can be synchronized across multipleclient devices of varying type, capabilities, operating systems, etc.Content synchronization service 156 can synchronize any changes (new,deleted, modified, copied, or moved content items) to content items in adesignated location of a file system of client device 150.

Content items can be synchronized from client device 150 to contentmanagement system 110, and vice versa. In embodiments in which clientdevice 150 initiates synchronization of content items with contentmanagement system 110, a user can manipulate content items directly fromthe file system of client device 150, while file system extension 156(which can be integrated with the local file system, or even theoperating system kernel) can intercept read, write, copy, move, deletecommands relative to content items in the designated location of thefile system of client device 150.

When file system extension 156 detects a write, move, copy, or deletecommand, it can notify content item synchronization service 156, whichcan synchronize the changes to content management system service 116. Insome embodiments, content item synchronization service 156 can performsome functions of content management system service 116 includingfunctions addressed above such as dividing a content item into blocks,hashing the content item to generate a unique identifier, etc. Contentsynchronization service 156 can index content within client storageindex 164 and save the result in storage index 164. Indexing can includecreating a unique identifier for each content item. In some embodiments,content synchronization service 156 creates this unique identifier byputting the data of the content item (e.g., excluding the filenameand/or other metadata) through a hash function; as addressed above,content management system can use a similar process to provideidentifiers to content on content management system 110. Contentsynchronization service 156 can use storage index 164 to facilitate thesynchronization of at least a portion of the content within clientstorage with content associated with a user account on contentmanagement system 110. For example, content synchronization service 156can compare storage index 164 with content management system 110 anddetect differences between content on client storage and contentassociated with a user account on content management system 110. Contentsynchronization service 156 can then attempt to reconcile differences byuploading, downloading, modifying, and/or deleting content on clientstorage as appropriate. Content management service 116 can store thechanged or new block for the content item and update server file journal148, metadata database 146, content directory 144, content storage 142,account database 140, etc., as appropriate.

When synchronizing content from content management system 110 to clientdevice 150, a modification, addition, deletion, and/or move of a contentitem recorded in server file journal 148 can trigger delivery of anotification to client device 150 using notification service 117. Whenclient device 150 receives the notification of the change to server filejournal 148, client device 150 can check storage index 164 to determineif the time stamp of the change occurred since the last synchronization,or determine if the specific change has been synchronized. When clientdevice 150 determines that it is out of synchronization with contentmanagement system 110, content item synchronization service 156 canrequest content item blocks including the changes, and client device 150can update its local copy of the changed content items. In someembodiments, notification service 117 can query other services ordatabases of content management system 110, such as server file journal148, to gain more context for the notification, to determine if anotification can be batched with another notification, or to supplementa notification, etc.

Sometimes client device 150 might not have a network connectionavailable. In this scenario, content item synchronization service 156can monitor the linked collection for content item changes and queuethose changes for later synchronization to content management system 110when a network connection is available. Similarly, a user can manuallystart, stop, pause, or resume synchronization with content managementsystem 110.

Content item synchronization service 156 can synchronize all contentassociated with a particular user account on content management system110. Alternatively, content item synchronization service 156 canselectively synchronize a portion of the content of the total contentassociated with the particular user account on content management system110. Selectively synchronizing only a portion of the content canpreserve space on client device 150 and improve performance of clientdevice 150 and content management system 110 by reducing the processing,memory, storage, and network resources that would otherwise be consumedby synchronizing all content.

In some embodiments, content item synchronization service 156selectively stores a portion of the content associated with theparticular user account and stores placeholder content items in clientstorage for the remainder portion of the content. For example, contentitem synchronization service 156 can store a placeholder content itemthat has the same filename, path, extension, metadata, of its respectivecomplete content item on content management system 110, but lacking thedata of the complete content item. The placeholder content item can be afew kilobytes or less in size while the respective complete content itemmight be significantly larger. After client device 150 attempts toaccess the content item, content item synchronization service 156 canretrieve the data of the content item from content management system 110and provide the complete content item to accessing client device 150.This approach can provide significant space and bandwidth savings whilestill providing full access to a user's content on content managementsystem 110.

Collaboration Features

Another feature of content management system 110 is to facilitatecollaboration between users. Collaboration features include content itemsharing, commenting on content items, co-working on content items,instant messaging, providing presence and seen state informationregarding content items, etc.

Sharing

Content management system 110 can manage sharing of content via sharingservice 128. Accounts of content management system 110 can share contentwith one another by providing a link to the content. Sharing service 128can then provide access to the shared content item from any computingdevice in network communication with content management system 110.However, in some embodiments, a link can be associated with accessrestrictions enforced by content management system 110. Sharing service128 can also facilitate indirect sharing of content within contentmanagement system 110 by enabling an account to share shared contentwith at least one additional user account (in addition to the originaluser account associated with the content item) so that each user accounthas access to the content item. The additional user account can gainaccess to the content by accepting the content, which will then beaccessible via web interface service 124 or the directory structureassociated with the additional user's account on client device 150. Thesharing can be performed in a platform agnostic manner. That is, thecontent can be shared across multiple client devices 150 of varyingtypes, capabilities, operating systems, etc. The content can also beshared across varying types of user accounts.

To share a content item within content management system 110 sharingservice 128 can add a user account identifier to a content entry inaccess control list database 145 associated with the content item, thusgranting the added user account access to the content item. Sharingservice 128 can also remove user account identifiers from a contententry to restrict a user account's access to the content item. Sharingservice 128 can record content item identifiers, user accountidentifiers given access to a content item, and access levels in accesscontrol list database 145.

To share content items outside of content management system 110, sharingservice 128 may generate a custom network address, such as a uniformresource locator (URL), which can allow any web browser to access thecontent item or collection in content management system 110 withoutauthentication. To accomplish this, sharing service 128 can includecontent identification data in the generated URL, which can later beused to properly identify and return the requested content item. Forexample, sharing service 128 can include the account identifier and thecontent path or a content item identifying code in the generated URL.Upon selection of the URL, the content identification data included inthe URL can be transmitted to content management system 110. Contentmanagement system 110 can then use the received content identificationdata to identify the appropriate content item and return the contentitem.

In addition to generating the URL, sharing service 128 can also recordthe URL in access control list database 145. In some embodiments, thecontent entry associated with a content item can include a URL flagindicating whether a URL to the content item has been created. Forexample, the URL flag can be a Boolean value initially set to 0 or falseto indicate that a URL to the content item has not been created. Sharingservice 128 can change the value of the flag to 1 or true aftergenerating a URL to the content item.

In some embodiments, sharing service 128 can associate a set ofpermissions to a URL for a content item. For example, if a user attemptsto access the content item via the URL, sharing service 128 can providea limited set of permissions for the content item. Examples of limitedpermissions include restrictions that the user cannot download thecontent item, save the content item, copy the content item, modify thecontent item, etc. In some embodiments, limited permissions includerestrictions that only permit a content item to be accessed from with aspecified domain, e.g., from within a corporate network domain, or byaccounts associated with a specified domain, e.g., accounts associatedwith a company account (e.g., @acme.com).

In some embodiments, sharing service 128 can also deactivate a generatedURL or otherwise unshare a content item. For example, each content entrycan also include an active sharing flag indicating whether the contentis still shared, and sharing service 128 may only return a requestedcontent item if the active sharing flag is set to 1 or true. Thus,access to a previously shared content item can be restricted by changingthe value of the active sharing flag. This can allow a user to restrictaccess to the shared content item without having to move the contentitem, delete the generated URL, etc. Likewise, sharing service 128 canreactivate sharing by again changing the value of the active sharingflag to 1 or true. A user can thus easily restore access to the contentitem without the need to generate a new sharing mechanism, e.g., a newURL.

In some embodiments, content management system 110 can designate alocation, such as a URL, for uploading a content item. For example, afirst user account can request for an upload location from sharingservice 128 a, provide the upload location to a second user account (orother user in some cases). The second user account or other user canupload a content item to the first user account using the uploadlocation.

Monitoring Interactions With Shared Content Items

In some embodiments, content management system 110 can provideinformation about user interactions with a shared content item. In someembodiments, content management system 110 can report that a user iscurrently viewing the shared content item. For example, clientcollaboration service 160 can request notifications service 117 to sendnotifications to other client devices having access to the sharedcontent item when any one client device accesses the shared contentitem. Notifications service 117 can then notify all client devicesregarding access to the shared content item by the one client device. Insome embodiments, the interaction data can also serve as a proxy for thepresence of a user owning and/or operating the one client device.

In some embodiments, content management system 110 can report a historyof user interactions with a shared content item. Collaboration service126 can query data sources such as metadata database 146 and server filejournal 148 to determine that a user account has saved the content item,that a user account has yet to access the content item, etc., anddisseminate this information using notification service 117 to otheruser accounts to determine which user accounts have (or have not)interacted with the shared content item.

In some embodiments, collaboration service 126 can facilitate commentingfor content, even if a content item does not natively support commentingfunctionality. Such comments can be stored in metadata database 146.

In some embodiments, collaboration service 126 can originate andtransmit notifications for users. For example, a first user can mentiona second user in a comment and collaboration service 126 can send anotification to the second user that he has been mentioned in thecomment. Various other content item events can trigger notifications,including deleting a content item, sharing a content item, etc.

In general, collaboration service 126 can provide a messaging platformwhereby users can send and receive instant messages, voice calls,emails, etc.

Collaboration on Content Items

Collaboration service 126 can also provide an interactive content itemcollaboration platform in which users can simultaneously make changes toshared content items, provide comments regarding the shared contentitems, manage tasks associated with the shared content items, etc. Theseshared content items can be files that user accounts can create and editusing a content item editor, and can contain elements for enablingcollaboration. These collaboration elements may include a collaborationidentifier, one or more author and/or editor identifiers, collaborationtext, collaboration attributes, interaction information, comments,sharing users, etc. The collaboration elements may be stored in databaseentries to allow for search and retrieval of the shared content items.Multiple user accounts may access, view, edit, and otherwise collaborateon shared content items at the same time or at different times. In someembodiments, this can be managed through a web interface that enablestwo users to work on the same copy of a shared content item at the sametime.

Collaboration Client Interface

In some embodiments, client collaboration service 160 can provide anative application interface for the purpose of displaying informationrelevant to a content item being presented on client device 150. In someembodiments, certain content items associated with a native applicationmay not be capable of presenting the collaboration data addressed above.In such embodiments, client collaboration service 160 can detect that auser has opened a content item, and can provide an overlay withadditional information for the content item, such as the collaborationdata. For example, the additional information can include comments forthe content item, a status of the content item, interactions with thecontent item by other users, etc. Such an overlay can warn a user thatchanges might be lost because another user is currently editing thecontent item.

In some embodiments, one or more of the services or storages/databasesdiscussed above can be accessed using public or private applicationprogramming interfaces.

Certain software applications can access content storage 142 via an APIon behalf of a user account. For example, a software package, such as anapplication running on client device 150, can programmatically make APIcalls directly to content management system 110 when a user accountprovides authentication credentials, to read, write, create, delete,share, or otherwise manipulate content.

A user can utilize a user account to view or manipulate content via aweb interface generated and served by web interface service 124. Forexample, the user can navigate in a web browser to a web addressassociated with the user account provided by content management system110. Changes or updates to content in content storage 160 made throughweb interface 124, such as uploading a new version of a content item,can be propagated back to other client devices associated with the useraccount. For example, multiple client devices, each with their ownclient software, can be associated with a single account and contentitems in the account can be synchronized between each of the multipleclient devices.

Client device 150 can connect to content management system 110 on behalfof a user account. A user of the user account can directly interact withclient device 150, for example when client device 150 is a desktop orlaptop computer, phone, television, internet-of-things device, etc.Alternatively or additionally, client device 150 can act on behalf ofthe user account without the user having physical access to clientdevice 150, for example when client device 150 is a server.

Some features of client device 150 are enabled by an applicationinstalled on client device 150. In some embodiments, the application caninclude a content management system specific component. For example, thecontent management system specific component can be a stand-aloneapplication 152, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 110 via a third-party application, such as a web browser, wordprocessor, spreadsheet program, presentation program, source codecontrol tool, etc. that resides on client device 150 and capable ofcommunicating with content management system 110. In variousimplementations, client-side application 152 can present a userinterface (UI) for a user to interact with content management system110. For example, the user can interact with the content managementsystem 110 via file system extension 153 integrated with the file systemor via a webpage displayed using a web browser application.

In some embodiments, client application 152 can manage and synchronizecontent for more than one account of content management system 110. Insuch embodiments, client application 152 can remain logged into multipleaccounts and provide normal services for the multiple accounts. In someembodiments, each account can appear as folder in a file system, and allcontent items within that folder can be synchronized with contentmanagement system 110. In some embodiments, client application 152 caninclude a selector to choose one of the multiple accounts to be theprimary account or default account.

While this disclosure presents content management system 110 withspecific components, it will be understood by one skilled in the art,that the architectural configuration of system 100 is simply onepossible configuration and that other configurations with more or fewercomponents are possible. Further, a service can have more or lessfunctionality, even including functionality described as beingassociated with another service. Moreover, features described in thisdisclosure with respect to a particular embodiment can be combined withfeatures described with respect to another embodiment.

While system 100 is presented with specific components, it will beunderstood by one skilled in the art, that the architecturalconfiguration of system 100 is simply one possible configuration andthat other configurations with more or fewer components are possible.

In some embodiments, sharing service 128 of content management system110 may also enable data loss prevention (DLP) features. For example,the sharing service 128 may store a DLP policy in account database 140.The DLP policy may contain a number of rules governing the use, sharing,or dissemination of content for a group or an individual. The rules mayinclude a condition that can be used to identify content items during ascan, and a restriction to govern how the identified content item willbe handled based on the DLP policy.

In some embodiments, the condition may include one or more keywords,regular expressions, or patterns. The conditions may be configured toidentify data that is typically considered sensitive or data that issensitive. For example, the conditions may include keywords such as“confidential,” “salary,” “secret,” “trade secret,” “do notredistribute,” “priviledged,” or other words or combinations of wordsthat typically accompany sensitive information. Patterns such asXXXX-XXXX-XXXX-XXXX for credit card numbers or XXX-XX-XXXX for socialsecurity numbers may also be included as conditions in the DLP policy.Other patterns for drivers license numbers, bank account numbers, phonenumbers, email addresses, addresses, or other personally identifiableinformation (PII) may also be used as conditions. Certain conditions maybe configured based on a particular use case or industry. For example,industry specific conditions may include the keywords “buy,” “sell,” or“short” in financial services industries or patterns for serial numbersof medical records in the medical industry.

The restriction is associated with one or more conditions and maydictate how content items found to violate the DLP based on theassociated conditions will be handled by content management system 110.Restrictions may include warnings, limitations on sharing, or otherrestrictions such as blocking an upload of an offending content item sothat it is not stored on content management system 110 or quarantiningthe content item. Restrictions may specify, for example, users will benotified or warned that the content item may contain sensitiveinformation when the content item is found or when the user attempts toshare or download the content item. Other restrictions may prohibitsharing of content items that violate certain conditions, prohibit thedownload of those content items, or limit sharing/downloading to onlymembers of a group.

In some embodiments, the content management system may enable certainDLP features to be active by default or enable an administrator (admin)to turn on the DLP features, customize the DLP policy, create DLP rules,or change any of the DLP settings. For example, an administrator on aclient device may activate DLP features in content management system 110for a group of users for which the administrator is responsible.

FIG. 2 shows an example graphical user interface 200 for enabling dataloss prevention (DLP) features in content management system 110according to some embodiments. Graphical user interface 200 may bepresented on a client-side application installed on a client device. Insome embodiments, the client-side application can include a contentmanagement system specific component. For example, the contentmanagement system specific component can be a stand-alone application,one or more application plug-ins, and/or a browser extension. However,the user can also interact with content management system 110 via athird-party application, such as a web browser, that resides on theclient device and is configured to communicate with content managementsystem 110.

Graphical user interface 200, as illustrated in FIG. 2, may be displayedto an administrator for a group of users of content management system110. For example, the administrator may be responsible for a company, adepartment, or other organization. Graphical user interface 200 includesan option 202 for the administrator to enable DLP features provided bycontent management system 110. Once the administrator selects the DLPoption 202, content management system 110 may allow the administrator toconfigure the DLP policy for the group.

FIG. 3 shows an example graphical user interface 300 for configuringdata loss prevention (DLP) features in content management system 110according to some embodiments. As illustrated in FIG. 3, graphical userinterface 300 may include options for conditions that the administratormay select. For example, the administrator may select a predefinedcondition 304 for credit card numbers that include the patternXXXX-XXXX-XXXX-XXXX or a predefined condition 306 for social securitynumbers that include the pattern XXX-XX-XXXX.

Graphical user interface 300 may also include a field 308 that allows anadministrator to define custom conditions. An administrator may inputkeywords (such as “Salary”), regular expressions, or patterns that maybe used to define a custom condition. Graphical user interface 300 mayalso include a number of restrictions 310 and 312 to be applied tocontent items that are identified based on the specified conditions. InFIG. 3, the restrictions include a restriction on sharing 310 contentitems identified based on the specified conditions and a restriction ondownloading 312 content items identified based on the specifiedconditions.

Although FIG. 3 illustrates embodiments where the administrator mayselect restrictions 310 and 312 that are applied to every selectedcondition, in some embodiments, the administrator may be able to applyrestrictions to specific conditions and other restrictions to otherconditions. For example, when defining the DLP policy, the administratormay choose to forbid sharing of content items that contain credit cardinformation and social security numbers but only restrict downloading ofcontent items that contain the term “salary.”

FIG. 2 and FIG. 3 illustrate example graphical user interfaces forenabling and configuring DLP features in content management system 110.In other embodiments, the graphical user interfaces may includeadditional elements, fewer elements, or alternative elements. Forexample, additional options may include predefined sets of conditionsfor certain use cases or industries or options for structured data.Structured data may include forms or other documents that have a typicalstructure (e.g., a check or purchase order). The structured data optionmay have predefined types of documents or allow the administrator toupload a form that may be used as a template for searching for otherdocuments that follow a similar structure. Certain embodiments may alsoallow the administrator to exclude certain documents from scanning suchas photos, audio files, videos, or documents with certain keywords, orpatterns. In other embodiments, the graphical user interfaces mayfurther include additional types of restrictions such as warnings tousers when content that meets the condition is uploaded, warnings tousers when the user attempts to share or download the content, blockingthe upload or storing of such content, or the quarantine of suchcontent.

Once the administrator is finished creating or updating a DLP policy,the administrator may save the changes 314 and the client-sideapplication installed on the client device may transmit the DLP policyto content management system 110 where sharing services 128 may storethe policy in account database 140. The policy may be stored as one ormore rules, where each rule includes one or more conditions used toidentify content items with sensitive data and one or more restrictionsto apply to content items that trigger the one or more conditions forthe rule.

If there was no previous DLP policy for the group, content managementsystem 110 may scan content items stored or managed by the contentmanagement system 110 for the group. The content management system 110may identify content items that meet the one or more conditions in theDLP policy and apply the appropriate restrictions based on the policy.

In some embodiments, a log of DLP policy violations may be generated andstored by at the content management system 110. The log of DLP policyviolations may include a record of each violation of the DLP policy andspecify the rule that was violated and the content item that violatedthe rule. Content items may also be scanned as content items areuploaded to content management system 110 or as changes are made tocontent items stored by content management system 110. If content itemsare found to be in violation of one or more rules of the DLP policy, arecord of the violation may be added to the log of DLP policyviolations. Additionally, if content items are no longer in violationbased on a change to the content item, the record for the violation maybe removed from the log.

If the administer removes a rule in the DLP policy, content managementsystem 110 may remove entries in the log of DLP violations pertaining tothe removed rule and update content item restrictions for the contentitems referenced in the removed entries, if necessary. If the administerupdates a rule in the DLP policy, content management system 110 mayidentify, based on the log of DLP violations, content items that haveviolated the previous version of the updated rule and rescan thesecontent items stored on content management system 110. The log of DLPviolations and the restrictions on these content items may then beupdated based on the result of the scan.

Because the content items are stored on content management system 110,content management system 110 is able to access the content items toperform the scanning or rescanning of the content items at any time, notonly during the uploading process or downloading process. Furthermore,the scans may be performed in the background or when computing resourcesare available and not cause additional delay for end users waiting toaccess content content. Furthermore, the log of DLP violations providesinformation on what rules content items have violated. As such, when arule is updated or removed, not all content items need to be rescanned.Instead, only those content items that should be rescanned based on thechanged rule can be rescanned and content items that violated rules thathave been removed can have their permissions updated without the needfor rescanning.

In some embodiments, content items may be shared with others by using alink generated by content management system 110. A scenario may occurwhere a user shares a content item with others using a link to thecontent item. After the user shares the link, an administrator maychange the DLP policy such that the content item may violate a rule inthe DLP policy. Content management system 110 may rescan the contentitem based on the change in DLP policy and restrict access to thecontent item based on the violation to the rule. Subsequent requests foraccess to the content item using the link will be goveners by the newrestrictions on the content item. Furthermore, an administrator mayagain change the DLP policy such that the content item is no longer inviolation. Content management system 110 may update the restrictions tothe content item such that access to the content item using the link isrestored. In such a way, access to the content item may stay up to datein a way not possible if the user sent a copy of the content item or ifa DLP service was unable to persistently access the content items toscan and modify restrictions to the content items stored on contentmanagement system 110.

The scanning and rescanning of content items may require some time andadditional computing resources. According to some embodiments, contentmanagement system 110 may use a flag to indicate that DLP restrictionsfor a content item is not up to date. For example, when a new DLP policyis created by an administrator or the administrator updates a DLPpolicy, each content item to be scanned may be flagged to indicate thatthe content item is not up to date. Content management system 110 willattempt to scan all content items that need to be scanned. However, insome cases, a content item may not be scanned before a user attempts touse the content item. Accordingly, if a user requests access a contentitem or requests to share a content item, content management system 110may determine if the requested content item is up to date based on theflag. If the content item is up to date, the user may access the contentitem as usual (e.g., based on the appropriate permissions andrestrictions). If the content item is not up to date based on the flag,content management system 110 may scan the requested content item andupdate the DLP restrictions for the content item based on the scanbefore providing usual access to the content item.

The scanning and rescanning of content items includes accessing thedigital data for the content item and searching the digital data forsomething that matches a condition in a rule of the DLP policy. Thedigital data is often in the form of a file, which may include metadataas a part of the file structure. However, in some cases, metadataassociated with a content item is stored separately from the digitaldata (e.g., the file) of the content item. As described above, contentitems may be stored in content storage 142 while some metadata may bestored in metadata database 146 of content management system 110.

For example, the collaboration platform provided by collaborationservice 126 enables users can simultaneously make changes to sharedcontent items, provide comments regarding the shared content items,manage tasks associated with the shared content items, etc. These sharedcontent items can be files that user accounts can create and edit usinga content item editor, and may be associated with elements for enablingcollaboration. These collaboration elements may include a collaborationidentifier, one or more author and/or editor identifiers, collaborationtext, collaboration attributes, interaction information, comments,sharing users, etc. The collaboration elements and other collaborationdata can be stored in metadata database 146, separate from contentstorage 142. According to some embodiments, persistent access to themetadata database 146 by content management system 110 enables contentmanagement system 110 to also search metadata stored in metadatabase 146that is associated with the content item being scanned to identifysomething that matches a condition in a rule of the DLP policy.

According to some embodiments collaborative content items may be createdon content management system 110 and reside permanently on contentmanagement system 110. Accordingly, there is no need for a user tocreate a content item and upload the content item to content managementsystem 110. Instead, the user can create the collaborative content itemon content management system 110 directly. The user can share thecollaborative content item with others by, for example, providing a linkto the content item. Other users may use the link to view, edit, orcomment on the collaborative content item on content management system110 if the users have permission to access the content item.Furthermore, other users may use the link to download a copy of thecollaborative content item, if permitted.

FIG. 4 shows an example graphical user interface 400 for accessingcontent items stored on content management system 110 according to someembodiments. Graphical user interface 400 shows 3 content items 402,404, and 406 that have been selected by a user. Content items 402, 404,and 406 may have been uploaded by another user or by the user viewinggraphical user interface 400. Two of the content items 402 and 404 areshown to contain sensitive content and have warning 412 and 414 thatinform the user that they contain sensitive content. The sensitivecontent may have been originally in content items 402 and 404 when theywere uploaded to content management system 110 or later added to contentitems 402 and 404 through online collaboration or editing of the contentitems.

Graphical user interface 400 of FIG. 4 shows the result of a userattempting to download content items containing sensitive content which,according to an example DLP policy, cannot be downloaded. For example, auser may attempt to download 408 the 3 selected content items 402, 404,and 406. Because at least one of the selected content items containssensitive content, the download of the content items is not allowed anda notification 410 is displayed informing the user that the download ofthe content items is not allowed. In some embodiments, contentmanagement system may allow for the download of content item 406, whichdoes not contain sensitive content.

FIG. 5 shows an example graphical user interface 500 for accessingcontent items stored on content management system 110 according to someembodiments. Graphical user interface 500 shows a list of content itemswhere one content item 502 is selected by the user. Based on a scan ofcontent items, content item 502 contains sensitive information.Accordingly, graphical user interface 500 includes a warning 504 thatinforms the user that content item 502 includes sensitive information.Furthermore, because sharing of content items with sensitive informationis prohibited under an example DLP policy, graphical user interface 500has disabled the sharing function 506 for content item 502. If the usermoves a cursor to the sharing function 506, a pop up 508 may bedisplayed that informs the user that the administrator has restrictedthe sharing of sensitive content.

According to some embodiments, content management system 110 may trackDLP activity, generate a DLP report, and provide the DLP report to groupadministrators. The report may include information about users thatadded content with sensitive information, how many content items withsensitive information a user added, or when a user added content withsensitive information. In some embodiments, content management system110 may also allow group administrators to suspend users that repeatedlyviolate DLP policy rules, suspend certain activities for users or forcertain content items, or approve sharing or downloading of certaincontent items containing sensitive information.

FIG. 6 shows an example graphical user interface 600 for displaying adata loss prevention (DLP) report according to some embodiments.Graphical user interface 600 may represent a DLP dashboard that isgenerated by content management system 110 and transmitted to a clientdevice associated with an administrator. The DLP dashboard may allow anadministrator to view DLP activity and filter or sort DLP informationbased on the type of activity 602, the user, the date, or the location.For example, the DLP dashboard displays information regarding 2incidents where user “Alex Bruce” added sensitive content. The DLPdashboard may also allow an administrator create various reports on DLPactivity 604.

FIG. 7 shows an example method 700 for providing data loss prevention(DLP) features in content management system 110 according to someembodiments. Although the methods and processes described herein may beshown with certain steps and operations in a particular order,additional, fewer, or alternative steps and operations performed insimilar or alternative orders, or in parallel, are within the scope ofvarious embodiments unless otherwise stated.

Method 700 may be implemented by content management system 110. Atoperation 705, content management system 110 may receive a DLP policyfrom a client device. The DLP policy may be received as a result of anadministrator enabling DLP features for a group of users of contentmanagement system 110 associated with a collection of content itemsstored by content management system 110. As illustrated in FIG. 2 andFIG. 3, the administrator may enable DLP features and define a DLPpolicy on the client device and transmit the policy to contentmanagement system 110 to be stored in account database 140. In someembodiments, the DLP policy may include one or more rules, where eachrule includes one or more conditions used to identify content items withsensitive data and one or more restrictions to apply to content itemsthat trigger the one or more conditions for the rule.

At operation 710, content management system 110 performs a scan ofcontent items associated with the group of users that the DLP policy isconfigured to govern and update the restrictions for the scanned contentitems if appropriate. For each rule in the DLP policy, the scanidentifies content items that satisfy the rule's one or more conditionsand applies the rule's restrictions. A content item found to satisfy theconditions for a rule may be considered in violation of that rule,according to the DLP policy. At operation 715, content management system110 generates a log of DLP violations based on the scan. The log of DLPpolicy violations may include a record of each violation of the DLPpolicy. For example, each record of a violation may specify the rulethat was violated and one or more content items that violated the rule.

Content management system 110 may determine whether an update to a rulein the DLP policy is received at operation 720. If there is no update toa rule in the DLP policy, at operation 725, content management system110 continues to scan content items, update restrictions for contentitems, and update the log of DLP violations based on changes to thecontent items. For example, if a user uploads a new content item tocontent management system 110, content management system 110 may scanthe content item based on the DLP policy, update any restrictions forthe uploaded content item based on the scan, and update the log of DLPviolations if appropriate. Similarly, if one or more users edits anexisting content item stored on content management system 110, contentmanagement system 110 may scan the edited content item based on the DLPpolicy, update any restrictions for the edited content item based on thescan, and update the log of DLP violations if appropriate.

If an update to a rule in the DLP policy is received by contentmanagement system 110, content management system 110 determines how arule was updated. Content management system 110 may perform differentoperations depending on how the rule was updated in order to moreefficiently rescan content items, update restrictions for content items,or update the log of DLP violations. For example, at operation 730,content management system 110 determines whether the update to the rulewas a removal of the rule. If so, the method continues in FIG. 8.

FIG. 8 shows an example method 800 for responding to the removal of arule from a DLP policy according to some embodiments. At operation 805,content management system 110 identifies, based on the log of DLPviolations, one or more content items that are restricted based on theremoved rule. For example, some content items may have been restrictedbased on violations of a particular rule in the DLP policy. Since theadministrator removed the rule from the policy, these restrictions basedon the violation of the removed rule should also be removed. Atoperation 810, content management system updates the restrictions forthe identified content items accordingly and, at operation 815, the logof DLP violations is updated by removing records associated withviolations of the removed rule.

Returning to FIG. 7, at operation 735, content management system 110determines whether the update to the rule was a change to a condition inthe rule. For example, an administrator may change a condition in anexisting rule or add a new rule with at least one new condition and oneor more restrictions to the DLP policy. If content management system 110detects a change to a condition, the method continues in FIG. 9.

FIG. 9 shows an example method 900 for responding to a change to acondition in a rule in a DLP policy according to some embodiments. Whena condition is changed in the DLP policy, rescanning of content items onthe content management system 110 and updating the restrictions for thecontent items based on the scan may be appropriate. However, dependingon the number of content items, the size of the content items, and thecomplexity of the scan, the rescanning and updating may not be completedfor all content items before a user requests access to one of thecontent items. According to some embodiments, content management system110 may use flags to indicate that DLP restrictions for some contentitems are not up to date.

For example, each content item entry may include a DLP outdated flagindicating whether the DLP restrictions for the content item is up todate. At operation 905, content management system 110 may set the DLPoutdated flag for all content items that need to be rescanned and beginrescanning the content items based on the change to the condition in theDLP policy. Rescanning of the content items may include scanning thecontents of each content item to determine whether the content itemsatisfies the changed condition, updating the restrictions for contentitems that satisfy the changed condition, and updating the log of DLPviolations based on the scan. After a content item is scanned, contentmanagement system 110 may remove the DLP outdated flag to indicate thatthe DLP restrictions for the content item is up to date.

Before the rescanning of content items is completed at operation 945,content management system 110 may receive a request for a content itemfrom a client device at operation 915. Content management system 110determines whether the DLP outdated flag for the requested content itemis set at operation 920. If the DLP outdated flag is not set, the DLPrestrictions for the content item is up to date. Accordingly, method 900continues to operation 940, where content management system 110 allowsthe client device access to the content item based on the existingrestriction.

If the DLP outdated flag is set, the DLP restrictions for the contentitem is not current. Accordingly, content management system 110 scansthe requested content item to determine whether the content itemsatisfies the changed condition at operation 925. The DLP restrictionsfor the requested content item are updated if the requested content itemsatisfies the changed condition and the log of DLP violations is updatedbased on the scan at operation 930. After a content item is rescanned,content management system 110 removes the DLP outdated flag at operation935 to indicate that the DLP restrictions for the content item is up todate and allows the client device access to the content item atoperation 940.

Returning to FIG. 7, at operation 740, content management system 110determines whether the update to the rule was a change to a restrictionin the rule. If so, the method continues in FIG. 10.

FIG. 10 shows an example method 1000 for responding to a change to arestriction in a rule in a DLP policy according to some embodiments. Insome embodiments, a change in the restrictions for a rule does notnecessitate a rescanning of all content items. Instead, only therestrictions for content items that violated the rule should be updatedbased on the changed restrictions. Accordingly, content managementsystem 110 may identify one or more content items that violated the rulebased on the log of DLP violations at operation 1005. At operation 1010,the restrictions for the identified content items are updated based onthe changed restriction.

FIG. 11 illustrates an example computing system architecture 1100wherein the components of the system are in communication with eachother using a connection 1105. Connection 1105 can be a physicalconnection via a bus, or direct connection into processor 1110 such asin a chipset architecture. Connection 1105 can also be a virtualconnection, networked connection, or logical connection.

In some embodiments, 1100 is a distributed system, wherein the functionsdescribed with respect to the components herein can be distributedwithin a datacenter, multiple datacenters, geographically, etc. In someembodiments, one or more of the described system components representsmany such components each performing some or all of the function forwhich the component is described. In some embodiments, the componentsdescribed herein can be physical or virtual devices.

Example system 1100 includes at least one processing unit (CPU orprocessor) 1110 and a connection 1105 that couples various systemcomponents including the system memory 1115, such as read only memory(ROM) and random access memory (RAM) to the processor 1110. The system1100 can include a cache of high-speed memory connected directly with,in close proximity to, or integrated as part of the processor 1110.

The processor 1110 can include any general purpose processor and ahardware service or software service, such as service 1 1132, service 21134, and service 3 1136 stored in storage device 1130, configured tocontrol the processor 1110 as well as a special-purpose processor wheresoftware instructions are incorporated into the actual processor design.The processor 1110 may essentially be a completely self-containedcomputing system, containing multiple cores or processors, a bus, memorycontroller, cache, etc. A multi-core processor may be symmetric orasymmetric.

To enable user interaction with the computing device 1100, an inputdevice 1145 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 1135 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 1100. The communications interface1140 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 1130 can be a non-volatile memory and can be a hard diskor other types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 1125, read only memory (ROM) 1120, andhybrids thereof.

The storage device 1130 can include software services, servers,services, etc., that when the code that defines such software isexecuted by the processor 1110, it causes the system to perform afunction. In some embodiments, a hardware service that performs aparticular function can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 1110, bus 1105, display 1135, and soforth, to carry out the function.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware services or services, alone or in combination with otherdevices. In some embodiments, a service can be software that resides inmemory of a client device and/or one or more servers of a contentmanagement system and perform one or more functions when a processorexecutes the software associated with the service. In some embodiments,a service is a program, or a collection of programs that carry out aspecific function. In some embodiments, a service can be considered aserver. The memory can be a non-transitory computer-readable medium.

In some embodiments, the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, solid state memory devices, flash memory, USB devices providedwith non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include servers,laptops, smart phones, small form factor personal computers, personaldigital assistants, and so on. Functionality described herein also canbe embodied in peripherals or add-in cards. Such functionality can alsobe implemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

What is claimed is:
 1. A method comprising: receiving a data lossprevention (DLP) policy from a client device, wherein the DLP policycomprises one or more rules; identifying, from a collection of contentitems stored on a content management system, a set of content items inviolation of the one or more rules, the set of content items inviolation of the one or more rules being identified based on metadataassociated with the collection of content items; and updating contentmanagement permissions for the set of content items in violation of theone or more rules.
 2. The method of claim 1, further comprising:accessing the collection of content items stored on the contentmanagement system to identify the set of content items in violation ofthe one or more rules, the collection being stored in a content storageof the content management system; and accessing metadata associated withthe collection of content items to identify the set of content items inviolation of the one or more rules, the metadata being accessed from ametadata database of the content management system.
 3. The method ofclaim 2, wherein the content storage is separate from the metadatadatabase.
 4. The method of claim 1, wherein the metadata comprises atleast one of comments, author identifiers, editor identifiers,collaboration attributes, or collaboration text.
 5. The method of claim1, further comprising: generating, based on the set of content items inviolation of the one or more rules, a log of DLP violations.
 6. Themethod of claim 1, further comprising: receiving an update to the one ormore rules in the DLP policy; identifying, based on the log of DLPviolations, one or more content items for updating content managementpermissions; and updating, based on the update to the one or more rules,content management permissions for the one or more content items.
 7. Themethod of claim 1, wherein identifying the set of content items inviolation of the one or more rules comprises: scanning the collection ofcontent items on the content management system; and scanning themetadata associated with the collection of content items.
 8. Anon-transitory computer-readable medium comprising: instructions that,when executed by a computing system, cause the computing system to:receive a data loss prevention (DLP) policy from a client device,wherein the DLP policy comprises one or more rules; identify, from acollection of content items stored on a content management system, a setof content items in violation of the one or more rules, the set ofcontent items in violation of the one or more rules being identifiedbased on metadata associated with the collection of content items; andupdate content management permissions for the set of content items inviolation of the one or more rules.
 9. The non-transitorycomputer-readable medium of claim 8, storing additional instructionsthat, when executed by a computing system, cause the computing systemto: access the collection of content items stored on the contentmanagement system to identify the set of content items in violation ofthe one or more rules, the collection being stored in a content storageof the content management system; and access metadata associated withthe collection of content items to identify the set of content items inviolation of the one or more rules, the metadata being accessed from ametadata database of the content management system.
 10. Thenon-transitory computer-readable medium of claim 9, wherein the contentstorage is separate from the metadata database.
 11. The non-transitorycomputer-readable medium of claim 8, wherein the metadata comprises atleast one of comments, author identifiers, editor identifiers,collaboration attributes, or collaboration text.
 12. The non-transitorycomputer-readable medium of claim 8, storing additional instructionsthat, when executed by a computing system, cause the computing systemto: generate, based on the set of content items in violation of the oneor more rules, a log of DLP violations.
 13. The non-transitorycomputer-readable medium of claim 8, storing additional instructionsthat, when executed by a computing system, cause the computing systemto: receive an update to the one or more rules in the DLP policy;identify, based on the log of DLP violations, one or more content itemsfor updating content management permissions; and update, based on theupdate to the one or more rules, content management permissions for theone or more content items.
 14. The non-transitory computer readablemedium of claim 8, wherein identifying the set of content items inviolation of the one or more rules comprises: scanning the collection ofcontent items on the content management system; and scanning themetadata associated with the collection of content items.
 15. A systemcomprising: a processor; and a non-transitory computer-readable mediumstoring instructions that, when executed by the system, cause the systemto: receive a data loss prevention (DLP) policy from a client device,wherein the DLP policy comprises one or more rules; identify, from acollection of content items stored on a content management system, a setof content items in violation of the one or more rules, the set ofcontent items in violation of the one or more rules being identifiedbased on metadata associated with the collection of content items; andupdate content management permissions for the set of content items inviolation of the one or more rules.
 16. The system of claim 15, whereinthe non-transitory computer-readable medium stores additionalinstructions that, when executed by the system, cause the system to:access the collection of content items stored on the content managementsystem to identify the set of content items in violation of the one ormore rules, the collection being stored in a content storage of thecontent management system; and access metadata associated with thecollection of content items to identify the set of content items inviolation of the one or more rules, the metadata being accessed from ametadata database of the content management system, wherein the contentstorage is separate from the metadata database.
 17. The system of claim15, wherein the metadata comprises at least one of comments, authoridentifiers, editor identifiers, collaboration attributes, orcollaboration text.
 18. The system of claim 15, wherein thenon-transitory computer-readable medium stores additional instructionsthat, when executed by the system, cause the system to: generate, basedon the set of content items in violation of the one or more rules, a logof DLP violations.
 19. The system of claim 15, wherein thenon-transitory computer-readable medium stores additional instructionsthat, when executed by the system, cause the system to: receive anupdate to the one or more rules in the DLP policy; identify, based onthe log of DLP violations, one or more content items for updatingcontent management permissions; and update, based on the update to theone or more rules, content management permissions for the one or morecontent items.
 20. The system of claim 15, wherein identifying the setof content items in violation of the one or more rules comprises:scanning the collection of content items on the content managementsystem; and scanning the metadata associated with the collection ofcontent items.